docs(actions): add workflow run status reference#44984
Conversation
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
|
This PR follows the direction requested in #34987: a dedicated reference-style article rather than a reusable snippet. I kept the scope small by documenting the workflow run lifecycle values, linking from the REST workflow-runs page, and calling out the two most confusing cases ( |
|
@happysnaker Hi, I'm willing to check in about the rest of this PR, but please don't alter our frontmatter formatting. We have it that way because it works for us and it will stop working for us if it's changed. Change that back, and I will get a review on the rest. |
|
This PR has been automatically closed because there has been no response to to our request for more information from the original author. Please reach out if you have the information we requested, or open an issue to describe your changes. Then we can reopen this PR and begin the review process. |
Why:
Closes: #34987
What's being changed (if available, include any code snippets, screenshots, or gifs):
This PR adds a dedicated Actions reference page for workflow run
statusandconclusionvalues, matching the approach requested in the issue discussion.Changes in this PR:
content/actions/reference/workflows-and-actions/workflow-run-statuses.mdstatusfilter values more easilyThe new page distinguishes lifecycle
statusvalues from finalconclusionvalues, and calls out two common sources of confusion:pendingis often caused by concurrency limitswaitingis often caused by deployment protection rules or required reviewsCheck off the following: